Industrial Ethernet is the term used to represent the industrial protocols that use the standard Ethernet physical layer and standard Ethernet protocols.
On an Industrial Ethernet network, you can connect:
oIndustrial devices (industrial protocols)
oNon-industrial devices (other Ethernet protocols)
For more information, refer to Industrial Ethernet User Guide.
Industrial Ethernet Architecture
This figure presents a typical Industrial Ethernet architecture:
A Control network
B Device network
2 Daisy-chained devices
3 Ethernet switch
4 I/O island (Modbus TCP)
5 Vision sensor (EtherNet/IP)
6 PC and HMI (TCP/UDP)
2, 4, and 5 Industrial Ethernet slave devices (EtherNet/IP / Modbus TCP)
This architecture is configurable with EcoStruxure Machine Expert.
The M241 Logic Controller can be connected simultaneously to the control network and the device network. To use this functionality, you must make a second Ethernet port available by adding a TM4ES4 expansion module to your configuration. The Ethernet port embedded on the logic controller then connects to the device network and the Ethernet port on the TM4ES4 connects to the control network.
If no TM4ES4 expansion module is added, the embedded Ethernet port on the M241 Logic Controller can be connected to either the control network or the device network.
Industrial Ethernet Description
|
M241 Logic Controller |
|
|---|---|
|
Features |
Description |
|
Topology |
Daisy chain and Star via switches |
|
Bandwidth |
10/100 Mbit/s |
|
EtherNet/IP Scanner |
|
|
Performance |
Up to 16 EtherNet/IP target devices managed by the logic controller, monitored within a timeslot of 10 ms |
|
Number of connections |
0...16 |
|
Number of input words |
0...1024 |
|
Number of output words |
0...1024 |
|
I/O communications |
EtherNet/IP scanner service Function block for configuration and data transfer |
|
Originator/Target |
|
|
Modbus TCP IOScanner |
|
|
Performance |
Up to 64 Modbus TCP slave devices managed by the logic controller, monitored within a timeslot of 64 ms. |
|
Number of connections |
0...64 |
|
Number of input words |
0...2048 |
|
Number of output words |
0...2048 |
|
I/O communications |
Modbus TCP IOScanner service Function block for data transfer |
|
Master/Slave |
|
|
Other services |
FDT/DTM/EDS management |
|
FDR (Fast Device Replacement) |
|
|
DHCP server |
|
|
Security management (refer to Security Parameters and Firewall Configuration) |
|
|
Modbus TCP server |
|
|
Modbus TCP client |
|
|
Web server |
|
|
FTP Server (FTP and TFTP protocols) |
|
|
SNMP |
|
|
EtherNet/IP adapter (controller as a target on EtherNet/IP)(1) |
|
|
EtherNet/IP Originator |
|
|
Modbus TCP server (controller as a slave on Modbus TCP)(1) |
|
|
IEC VAR ACCESS |
|
|
Additional features |
Possible to mix up to 16 EtherNet/IP and Modbus TCP server devices. Devices can be directly accessed for configuration, monitoring, and management purposes. Network transparency between control network and device network (logic controller can be used as a gateway). NOTE: Using the logic controller as a gateway can impact the performance of the logic controller. |
|
(1) You must add a TM4ES4 expansion module to your logic controller to use this service in addition to the EtherNet/IP Scanner or Modbus TCP IOScanner features. |
|
EtherNet/IP is the implementation of the CIP protocol over standard Ethernet.
The EtherNet/IP protocol uses an originator/target architecture for data exchange.
Originators are devices that initiate data exchanges with target devices on the network. This applies to both I/O communications and service messaging. This is the equivalent of the role of a client in a Modbus network.
Targets are devices that respond to data requests generated by originators. This applies to both I/O communications and service messaging. This is the equivalent of the role of a server in a Modbus network.
EtherNet/IP Adapter is an end-device in an EtherNet/IP network. I/O blocks and drives can be EtherNet/IP Adapter devices.
The communication between an EtherNet/IP originator and target is accomplished using an EtherNet/IP connection.
The Modbus TCP protocol uses a client/server architecture for data exchange.
Modbus TCP explicit (non-cyclic) data exchanges are managed by the application.
Modbus TCP implicit (cyclic) data exchanges are managed by the Modbus TCP IOScanner. The Modbus TCP IOScanner is a service based on Ethernet that polls slave devices continuously to exchange data, status, and diagnostic information. This process monitors inputs and controls outputs of slave devices.
Clients are devices that initiate data exchange with other devices on the network. This applies to both I/O communications and service messaging.
Servers are devices that address any data requests generated by a Client. This applies to both I/O communications and service messaging.
The communication between the Modbus TCP IOScanner and the slave device is accomplished using Modbus TCP channels.
Adding the Industrial Ethernet Manager
The Industrial_Ethernet_manager must be present on the Ethernet_1 (Ethernet Network) node of the device tree to activate these functions and services:
oEtherNet/IP Scanner
oModbus TCP IOScanner
If Ethernet_1 (Ethernet Network) is already in use, you must add a TM4ES4 expansion module to your controller and move the EthernetIP or Modbus TCP slave device nodes from Ethernet_1 (Ethernet Network) to the TM4ES4 node.
The Industrial_Ethernet_manager is automatically added when a slave device is added on the Ethernet_1 (Ethernet Network) node.
|
Step |
Action |
|---|---|
|
1 |
In the Devices Tree, select Ethernet_1 (Ethernet Network) and click the green plus button of the node or right-click Ethernet_1 (Ethernet Network) and execute the Add Device command from the contextual menu. Result: The Add Device dialog box opens. |
|
2 |
In the Add Device dialog box, select Protocol Managers > Industrial Ethernet manager. |
|
3 |
Click the Add Device button. |
|
4 |
Click the Close button. |
For more information, refer to Industrial Ethernet Manager Configuration, EtherNet/IP Target Settings and Modbus TCP Settings.
